Require visible Telegram artifacts#243
Draft
MagMueller wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/home/bux/...pathsValidation
git diff --checkDraft because this is a prompt behavior change and should be reviewed before merging.
Summary by cubic
Update the system prompt so Telegram users receive the actual artifacts (reports, prep notes, audits, decks, screenshots) as Telegram documents or images, not just links to local paths. Local paths like
/home/bux/...are kept only as secondary provenance and must never be the only way to access the work.Written for commit 6a2a7ff. Summary will update on new commits. Review in cubic